Sharing rights to control aspects of an electronic message

ABSTRACT

A server may receive a request from a creator of a message to share one or more rights of the creator of the message with a user referenced in the message. In response to the request, the server may send a notification to the user referenced in the message. The notification includes an option to accept the one or more rights. The server may receive, from a user device of the user, an acceptance of the one or more rights and perform an operation related to the message based on the rights accepted by the user.

TECHNICAL FIELD

Aspects and implementations of the present disclosure relate toelectronic documents, and more specifically, to sharing rights tocontrol aspects of an electronic message.

BACKGROUND

Various known messaging platforms exist for users to exchange messages,such as electronic mail (email) systems, social network platforms, videoconferencing (e.g., video chat) platforms, etc. Using a messagingplatform, a creator may send an electronic message to a user andreference the user in the message. The electronic message may be anysuitable message, such as an electronic mail (email) in an email systemor a post in a social network platform, among others. For example, acreator may create a post that mentions a user and congratulates thatuser for a job well done. Other users associated with the creator and/orthe user can view the post and reply or react to the post. Likewise,other users copied on the email congratulating/celebrating the user canreply to everyone copied on the email with a response to the email.

SUMMARY

Aspects and implementations of the present disclosure relate to acreator of a message sharing one or more of his/her rights with respectto the message and/or feedback to the message with a user referenced inthe message. That is, the techniques enable sharing control typicallyreserved for a creator of a message with a user referenced in themessage. The message may be any suitable message, such as an email in anemail system or a post in a social network platform, among others. Forexample, a creator may enter a post that mentions a user andcongratulates that user for a job well done. The creator may set thispost as a celebratory/congratulatory post and select one or more rightsto share with the user mentioned. Additionally, the content of the postmay be analyzed to determine that the post is celebratory/congratulatoryand a recommendation may be sent to the creator to share the rights. Anotification may be sent to the user mentioned, prompting them to acceptor decline the one or more rights.

The rights may include enabling the mentioned user to receive (e.g.,reaction, comment, etc.) notifications related to feedback to the postby other users. The rights may include the ability to control whetherthe post is visible to an entire group the post is shared with or asubset of users (e.g., just the mentioned user, the creator, people inthe group with certain titles, etc.) of the group. The rights may alsoinclude controlling whether users can provide feedback (e.g., react,comment, etc.) with the post; and the type of feedback allowed for theusers.

According to one aspect of the present disclosure there is provided amethod comprising: receiving, at a server, a request from a creator of amessage to share one or more rights of the creator of the message with auser referenced in the message, wherein the message is for a pluralityof users and the user; in response to the request, sending, by theserver, a notification to the user referenced in the message, whereinthe notification includes an option to accept the one or more rights;receiving, at the server from a user device of the user, an acceptanceof the one or more rights; and performing, by the server, one or moreoperations related to the message based on the one or more rightsaccepted by the user.

The message may be at least one of a social media post in a socialnetwork platform, an email in an email system, or a text or multimediamessage in a text messaging platform or a video conferencing platform.

The one or more operations may comprise sending a feedback notification,based on feedback related to the message, to the user based on the oneor more rights accepted by the user.

The performing one or more operations may comprise preventing otherusers of the plurality of users from seeing the message based on a firstrule set by the user with respect to the one or more rights, orpreventing other users of the plurality of users from seeing feedback tothe message based on a second rule set by the user with respect to theone or more rights.

The performing the one or more operations may comprise sending afeedback notification exclusively to the user referenced in the messagein response to a second user of the plurality of users providingfeedback to the message.

The performing the one or more operations may comprise sending afeedback notification exclusively to the creator and the user referencedin the message in response to a second user of the plurality of usersproviding feedback to the message.

The receiving, from the user device of the user, the acceptance of theone or more rights may further comprise setting one or more rulesspecifying one or more of sending notifications related to any responsesto the message to a subset of the plurality of users, controllingvisibility of the message, controlling visibility of feedback to themessage, controlling whether feedback is allowed for the message,controlling what type of feedback is allowed for the message, orcontrolling who can provide feedback for the message.

The request may include a property indicating the message being of atype of message that specifies to share the one or more rights of thecreator of the message with the user identified in the message.

The method may further comprise: analyzing content of the message toidentify if the message comprises one or more keywords indicative of aparticular type of message; and based on the message comprising at leastone of the one or more keywords, sending a second notification to thecreator of the message, wherein the second notification inquires whetherthe creator desires to share the one or more rights with the user andthe second request is received as a response to the second notification.

The method may further comprise: receiving, at the server from the userdevice of the user, a request for the creator to share the one or morerights with the user; and sending a second notification to the creatorof the message, wherein the second notification inquires whether thecreator desires to share the one or more rights with the user and thesecond request is received as a response to the second notification.

The one or more rights may specify one or more of whether the user is toreceive feedback notifications of feedback related to the message,whether the user is to control visibility of feedback on the message byusers, or whether the user is to control allowing feedback on themessages.

The one or more operations may be performed in response to a second userof the plurality of users providing feedback on the message, wherein thefeedback comprises a reaction or a comment.

According to another aspect of the present disclosure there is provideda system comprising: a memory device; and a processing deviceoperatively coupled to the memory device, the processing device to:receive a request from a creator of a message to share one or morerights of the creator of the message with a user referenced in themessage, wherein the message is for a plurality of users and the user;in response to the request, send a notification to the user referencedin the message, wherein the notification includes an option to acceptthe one or more rights; receive, from a user device of the user, anacceptance of the one or more rights; and perform one or more operationsrelated to the message based on the one or more rights accepted by theuser.

The message may be at least one of a social media post in a socialnetwork platform, an email in an email system, or a text or multimediamessage in a text messaging platform or a video conferencing platform.

The performing one or more operations may include the processing devicefurther to prevent other users of the plurality of users from seeing themessage based on a first rule set by the user with respect to the one ormore rights, or preventing other users of the plurality of users fromseeing feedback to the message based on a second rule set by the userwith respect to the one or more rights.

The receiving, from the user device of the user, the acceptance of theone or more rights may further comprise setting one or more rulesspecifying one or more of sending notifications related to any responsesto the message to a subset of the plurality of users, controllingvisibility of the message, controlling visibility of feedback to themessage, controlling whether feedback is allowed for the message,controlling what type of feedback is allowed for the message, orcontrolling who can provide feedback for the message.

The request may include a property indicating the message being of atype of message that specifies to share the one or more rights of thecreator of the message with the user identified in the message.

According to another aspect of the present disclosure there is provideda non-transitory, computer readable media storing instructions that,when executed, cause a processing device to perform the method stepsdescribed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects and implementations of the present disclosure will be understoodmore fully from the detailed description given below and from theaccompanying drawings of various aspects and implementations of thedisclosure, which, however, should not be taken to limit the disclosureto the specific aspects or implementations, but are for explanation andunderstanding only.

FIG. 1 illustrates an example of a system architecture forimplementations of the present disclosure.

FIG. 2 depicts a flow diagram of aspects of a method for sharing one ormore rights of a creator of a message with a user referenced in themessage, in accordance with one implementation of the disclosure.

FIG. 3 illustrates an example post referencing a user where the postprovides options for sharing rights with the referenced user, inaccordance with one implementation of the disclosure.

FIG. 4 illustrates an example notification requesting a user referencedin a post to accept or decline shared rights, in accordance with oneimplementation of the disclosure.

FIG. 5 illustrates example options available for a user to specify userrules for posts in which the user is referenced, in accordance with oneimplementation of the disclosure.

FIG. 6 illustrates an example post that references a user and providesan option to positively react to the post to another user, in accordancewith one implementation of the disclosure.

FIG. 7 illustrates an example notification sent to the user referencedin the post when the other user positively reacts to the postreferencing the user, in accordance with one implementation of thedisclosure.

FIG. 8 illustrates an example post that references a user and providesan option to respond to the post to another user, in accordance with oneimplementation of the disclosure.

FIG. 9 illustrates an example notification sent to the user referencedin the post when the other user responds to the post referencing theuser, in accordance with one implementation of the disclosure.

FIG. 10 depicts a flow diagram of aspects of a method for analyzingcontent of a message and sending a notification to a creator of themessage inquiring whether the creator desires to share rights with auser referenced in the message, in accordance with one implementation ofthe disclosure.

FIG. 11 depicts a flow diagram of aspects of a method to allow a user torequest a creator to share rights to a message in which the user isreferenced, in accordance with one implementation of the disclosure.

FIG. 12 depicts a block diagram of an example computing system operatingin accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

Messaging platforms may allow a creator to input an electronic message,reference or mention one or more users in the electronic message, andsend the electronic message to a group of people (e.g., including theuser, the creator, other users, etc.), among other things. The terms“mention” and “reference” may be used interchangeably herein.Referencing a user in the electronic message may refer to associatingthe user with the contents of the message. For example, one messagingplatform may include an email system and the electronic message may bean electronic mail (email). Another example messaging platform mayinclude a social network platform and the electronic message may be apost on the social network platform. Yet other example messagingplatforms may include a text messaging (e.g., text chat) platform orvideo conferencing (e.g., video chat) platform and the electronicmessage may be a text message (e.g., Short Message Service (SMS)message) or an image or video message (e.g., Multimedia MessagingService (MEMS) message). In some instances, the creator may congratulateor celebrate the referenced user in the message.

A technical problem which may be addressed by embodiments of the presentdisclosure is that a large amount of network traffic occurs when anumber of messages are created and sent to users in a group within whicha congratulatory/celebratory message is sent. For example, when acreator sends an email to congratulate a user and copies a large numberof people on the email, oftentimes the people ‘reply all’ to the emailand flood everyone in the group's inboxes. In another example, when acreator makes a post congratulating a user B on a social network, andusers C and D “like” the creator's post, network resources may beincurred when informing the creator of the “likes” of users C and D andalso when users C and D send their own congratulatory message to user B(because user B may not be notified of the “likes” of users C and D).

Another technical problem which may be addressed by embodiments of thedisclosure is protecting certain data from being accessible to certainpeople. For example, the congratulatory message or the responses to thecongratulatory message may include data that the user mentioned in theemail does not desire to be shared with the entire group if it issensitive or confidential.

To address the above identified technical problems embodiments mayinclude a creator of a message sharing rights with a user referenced inthe message. The rights may enable the referenced user to set up rulesthat enable performing one or more operations related to the messageand/or to feedback of the message. The rights may enable the userreferenced in the message to control the level of engagement with themessage that is to be provided to other users. For example, when themessage is created and a user is referenced in the message, one or morerights may be shared with the referenced user. The shared rights may beapplied by the referenced user to set up rules to receive or not receivenotifications related to feedback to the message, to control thevisibility of the message and/or feedback on the message by others, tocontrol whether users and/or which users can provide feedback on themessage, to control the type of feedback allowed with the message,and/or the like. As such, embodiments of the disclosure may relate tocontrolling a level of access to data.

Advantageously, embodiments of the present disclosure may reduce thenumber of messages that are created and sent to users associated with amessage. For example, in some instances the mentioned user may set up arule such that the user and/or creator of the message are the only usersof the group to receive feedback notifications to the message, therebypreventing messages from being sent to the other users in the group.Furthermore, considering the example above, by informing user B of the“likes” of users C and D, this operates as a way for user C and D tocongratulate user B. Thus, users C and D may not send separatecongratulatory messages to user B, which thereby reduces the amount ofnetwork resources that may otherwise be incurred.

Furthermore access to data contained in messages and/or feedback tomessages may be controlled, thereby protecting the content that the userconsiders to be private or sensitive. This may prevent the datacontained in messages from being accessible to malicious users of asocial network (e.g. a third party, a “bot” etc.).

FIG. 1 illustrates an example of a system architecture 100 forimplementations of the present disclosure. The system architecture 100includes a cloud-based environment 110 connected to user devices120A-120Z via a network 130. A cloud-based environment 110 refers to acollection of physical machines that host applications providing one ormore services (e.g., content management) to multiple user devices 120via a network 130. The network 130 may be public networks (e.g., theInternet), private networks (e.g., a local area network (LAN) or widearea network (WAN)), or a combination thereof. Network 130 may include awireless infrastructure, which may be provided by one or more wirelesscommunications systems, such as a wireless fidelity (WiFi) hotspotconnected with the network 130 and/or a wireless carrier system that canbe implemented using various data processing equipment, communicationtowers, etc. Additionally or alternatively, network 130 may include awired infrastructure (e.g., Ethernet).

The cloud-based environment 110 may include one or more servers112A-112Z and a data store 114. The data store 114 may be separate fromthe servers 112A-112Z and communicatively coupled to the servers112A-112Z or the data store 114 may be part of one or more of theservers 112A-112Z. In some embodiments, the data store 114 may beincluded as part of the user devices 120A-120Z. The data store 114 maystore messages 113 (e.g., email messages, text or video messages, postson social network platforms, etc.), rights 115 to control aspects of themessages 113 and/or feedback to the messages 113, and/or user rules 117.Such rights conventionally may be reserved to a creator of the messages113, but according to techniques of the present disclosure, one or moreof the rights 115 may be shared with a user mentioned in a message 113.The disclosure provides a fine grained mechanism to allow a user tocontrol whether the referenced user receives notifications related toresponses/reactions to the messages 113 they are referenced in, whichusers and/or groups can interact (e.g., respond, react, etc.) with themessages 113 they are referenced in, which users and/or groups can viewthe messages 113 and/or responses/reactions to the messages 113, and soforth.

Thus, the rights 115 may enable the mentioned user to receivenotifications related to feedback (e.g., reaction, comment, etc.) to thepost by other users, to control whether the post is visible to certainusers, to control whether users can provide feedback (e.g., react,comment, etc.) for the messages 113, and/or to control the type offeedback allowed for the users. In some embodiments, the mentioned usermay be prompted with a notification that requests the mentioned user toaccept the one or more rights that are being shared by the creator. Ifthe user accepts the rights 115, the user can configure one or more userrules 117. The user rules 117 may specify that just the mentioned useris to receive notifications about feedback to the message 113 and notthe creator or any other user associated with the group to which themessage 113 was sent. Another user rule 117 may specify that just acertain group of users can view the message 113 and/or provide feedbackto the message 113. Further, another user rule 117 for the type offeedback allowed to one or more messages 113 can specify that justcomments are allowed on the one or more messages 113 but not reactionsto the one or more messages 113.

The servers 112A-112Z may be physical machines (e.g., server machines,desktop computers, etc.) that each include one or more processingdevices communicatively coupled to memory devices and input/output (I/O)devices. The servers 112A-112Z may host a messaging platform(118A-118Z). The messaging platform 118 may be an electronic mailsystem, a social network platform, a text messaging platform, a videomessaging platform, a video conference platform, or the like. Themessaging platform 118 may be implemented as computer instructions thatare executable by one or more processing devices on each of the servers112A-112Z. In alternative implementations, the messaging platforms118A-118Z may be installed on the user devices 120A-120Z (e.g., as astandalone application) and operate as peers in a peer-to-peerenvironment. In yet alternative implementations, applications on theuser devices 120A-120Z may interact with the messaging platform 118 andmay perform some of the functionality of the messaging platform 118.

One or more of the servers 112A-112Z may host the messaging platform118A-118Z. The server 112A-112Z selected to host the messaging platform118A-118Z may be based on certain load-balancing techniques, servicelevel agreements, performance indicators, or the like. It should beunderstood that the servers 112A-112Z of the cloud-based environment 110host the messaging platforms 118A-118Z, and thus, the messagingplatforms 118A-118Z may be referred to as cloud-based messagingplatforms 118A-118Z herein.

The messaging platform 118A-118Z may enable a creator to create, edit,view, and/or send a message 113 within a respective user interface124A-124Z. The messaging platform 118A-118Z may also enable the creatorto reference one or more users in the message 113 and select an optionto make the message 113 a particular message type (e.g., celebratory,congratulatory, etc.) within the respective user interface 124A-124Z andrequest that one or more rights 115 be shared with the user referencedin the message 113. The messaging platform 118A-118Z may also enable thecreator to receive notifications when the user requests the rights 115,when the user accepts or declines the rights 115, when other usersprovide feedback to the messages 115, and so forth, within the userinterface 124A-124Z. The messaging platform 118A-118Z may also enable auser to accept the shared rights 115 via a notification provided withinthe respective user interface 124A-124Z. The messaging platform118A-118Z may also enable a user to set up user rules 117 for themessages 113 within the respective user interface 124A-124Z. Themessaging platform 118A-118Z may also enable a user to receivenotifications when other users provide feedback to the messages 113 inwhich the user is referenced within the respective user interface124A-124Z. The messaging platform 118A-118Z may also enable a user toselect various other options related to the message (e.g., request therights 115 to the message 113) within the respective user interface124A-124Z. The messaging platform 118A-118Z may also analyze content ofa message to determine whether it is a particular message type (e.g.,celebratory), and if so determined to be that particular message type,provide a notification to a creator to share rights 115 with a userreferenced in the message 113.

The messaging platform 118A-118Z may also enable users (e.g., themessage creator, the referenced user, other users associated with themessage 113) using different user devices 120A-120Z to simultaneouslyaccess the messages 115 to comment on, react (e.g., like, dislike,laugh, upset, etc.) to, and/or view the message 113 in a respective userinterface 124A-124Z that presents the message 113 and/or feedback to themessage 113. In an implementation, the user interfaces 124A-124Z of themessaging platform 118A-118Z may be web pages rendered by a web browserand displayed on the user device 120A-120Z in a web browser window. Inanother implementation, the user interfaces 124A-124Z may be displayedby a mobile application or a desktop application. For example, the userinterfaces 124A-124Z may be displayed by a native application executingon the user device 120A-120Z. The native application may be separatefrom a web browser.

The user devices 120A-120Z may include one or more processing devicescommunicatively coupled to memory devices and I/O devices. The userdevices 120A-120Z may be desktop computers, laptop computers, tabletcomputers, mobile phones (e.g., smartphones), or any suitable computingdevice. As discussed above, the user devices 120A-120Z may each includea web browser and/or a client application (e.g., a mobile application ora desktop application).

FIG. 2 depicts a flow diagram of aspects of a method 200 for sharing oneor more rights 115 of a creator of a message 113 with a user referencedin the message 113, in accordance with one implementation of thedisclosure. It should be noted that the user device 120A and the userinterface 124A are used for discussion related to a creator, the userdevice 120B and the user interface 124B are used for discussion relatedto a user referenced in the message 113, and a user device 120C and theuser interface 124C are used for discussion related to other users towhich the message is sent. Method 200 and each of its individualfunctions, routines, subroutines, or operations may be performed by oneor more processing devices of the computer device executing the method.In certain implementations, method 200 may be performed by a singleprocessing thread. Alternatively, method 200 may be performed by two ormore processing threads, each thread executing one or more individualfunctions, routines, subroutines, or operations of the method. In anillustrative example, the processing threads implementing method 200 maybe synchronized (e.g., using semaphores, critical sections, and/or otherthread synchronization mechanisms). Alternatively, the processesimplementing method 200 may be executed asynchronously with respect toeach other.

For simplicity of explanation, the methods of this disclosure aredepicted and described as a series of acts. However, acts in accordancewith this disclosure can occur in various orders and/or concurrently,and with other acts not presented and described herein. Furthermore, notall illustrated acts may be required to implement the methods inaccordance with the disclosed subject matter. In addition, those skilledin the art will understand and appreciate that the methods couldalternatively be represented as a series of interrelated states via astate diagram or events. Additionally, it should be appreciated that themethods disclosed in this specification are capable of being stored onan article of manufacture to facilitate transporting and transferringsuch methods to computing devices. The term “article of manufacture,” asused herein, is intended to encompass a computer program accessible fromany computer-readable device or storage media. In one implementation,method 200 may be performed by the messaging platform 118A-118Z executedby one or more processing devices of the server 112A-112Z. In anotherimplementation, method 200 may be executed by a client applicationexecuted by one or more processing devices of the user devices120A-120Z.

At block 202, the processing device may receive a first request from acreator to create a message 113 that references a user (exampleillustrated in FIG. 3). The creator may also select to send the message113 to a group of users including the referenced user. For example, themessage 113 may be a social media post in a social network platform, themessage 113 may be an email in an email system, or the message 113 maybe a text or video message in a text messaging system or video chatsystem. To send an email to other users, the user can copy theadditional users on the email message, to send a post to other users,the user may share the post with a specific group of people or with thepublic, and/or to send a text or video message to other users, the usermay share a text or multimedia (e.g., image and/or video) message with aspecific group of people or with other participants of a video chat.

The creator may select to create the message 113 via options provided bythe user interface 124A of the messaging platform 118A. Within thecontent of the message 113, the creator may reference a user using avisual indicator (e.g., hashtag, plus sign, etc.) that causes thereferenced user to be associated with the message 113. Further, thecreator may select to make the message 113 a particular message type,such as a celebratory or congratulatory message. Choosing thisparticular message type may cause various options for sharing rights 115to the message 113 with the referenced user to be presented via the userinterface 124A. The creator can select one or more of the rights 115, asdescribed further below.

At block 204, the processing device may receive a second request fromthe creator of the message to share the one or more rights 115 of thecreator of the message 113 with the user referenced in the message 113(example illustrated in FIG. 3). In some embodiments, the second requestand the first request may be combined into a single request and/orreceived at the same time. Alternatively, the message referencing theuser may be an existing message, and therefore the first request may notbe used and only the second request may be received with respect to theexisting message referencing the user. The rights 115 may specify one ormore of whether the referenced user can receive feedback notificationsto feedback (e.g., comments, responses, reactions, etc.) related to themessage 113, whether the user can control visibility of feedback on themessage 113 by other users, whether the user can control allowingfeedback on the message 113, and/or what type of feedback is allowed forthe message 113.

The second request may include a property indicating a type of messagethat specifies to share the one or more rights 115 of the creator of themessage 113 with the user identified (e.g., reference) in the message.In an implementation, the creator can select this property when creatingthe message 113 via the user interface 124A, and the creator selectingto send the message 113 may cause the first and second requests to besent from a user device 120A of the creator and received by theprocessing device.

In an implementation, the user referenced in the message 113 may selectto request the rights 115 via an option related to the message 113provided by the user interface 124B. This scenario may occur when thecreator did not request to share the rights 115 or forgot to request toshare the rights 115. The processing device may receive, from a userdevice 120B of the user, a request for the creator to share the one ormore rights 115 with the user. The processing device may send anotification to the user device 120A of the creator of the message 113,and the notification may request whether the creator desires to sharethe one or more rights 115 with the user referenced in the message 113.If the creator selects to share the rights 115, the processing devicemay receive the second request from the creator of the message 113 toshare the rights 115 with the user referenced in the message 113. If thecreator declines to share the rights 115, then the rights 115 may not beshared with the user.

In an implementation, the processing device may analyze content of themessage to identify one or more keywords (e.g., “congratulations,” “welldone,” “way to go,” etc.) indicative of a particular message type (e.g.,celebratory, congratulatory, etc.). The processing device may send anotification to the creator of the message 113 in response todetermining that the message 113 is the particular message type. Thenotification may request whether the creator desires to share one ormore rights 115 with the user referenced in the message 113. If thecreator selects to share the rights 115, the processing device mayreceive the second request from the creator of the message 113 to sharethe rights 115 with the user referenced in the message 113. If thecreator declines to share the rights 115, then the rights 115 may not beshared with the user.

In some implementations, a user to which the message 113 is sent mayview the message and determine that they should be referenced in themessage. The user interface 124B may provide an option for the user torequest to be referenced in the message 113. The processing device mayreceive the request and send a notification to the user interface 124Aof the creator to request whether the creator desires to reference theuser in the message 113. If the creator selects to reference the user,the user may be referenced in the message 113. Further, the creator maybe presented with the options to share the rights 115 with the user. Ifthe creator selects to share the rights 115, the processing device mayreceive the second request from the creator of the message 113 to sharethe rights 115 with the user referenced in the message 113.

In some implementations, the message 113 referencing the user may not beset to the particular message type when created. Other users may respondto the message 113 by commenting or reacting, etc. The processing devicemay analyze the content of the responses (e.g., via keywords, etc.), andif the content satisfies criteria (e.g., includes certain keywordsindicating a celebratory or congratulatory message), the processingdevice may send a notification to the creator of the message 113 inresponse to determining that the message 113 is the particular messagetype. The notification may request whether the creator desires to shareone or more rights 115 with the user referenced in the message 113. Ifthe creator selects to share the rights 115, the processing device mayreceive the second request from the creator of the message 113 to sharethe rights 115 with the user referenced in the message 113. If thecreator declines to share the rights 115, then the rights 115 may not beshared with the user.

In some implementations, viewers (e.g., a referenced user in the message113 and/or a non-referenced user in the message 113) of responses (e.g.,comments, reactions, etc.) to the message 113 may determine that themessage 113 should be set to the particular message type and recommendthe message 113 be set to the particular message type. Accordingly, insome embodiments, the user interface 124B may provide an option for theuser to send a notification to the creator of the message to set themessage 113 to the particular message type and share the one or morerights 115. The processing device may receive the notification and sendanother notification to the user interface 124A of the creator torequest whether the creator desires to set the message 113 to theparticular message type and/or to share one or more rights 115 with theuser referenced in the message 113. If the creator selects to set themessage 113 to the particular message type and share the rights 115, theprocessing device may receive the second request from the creator of themessage 113 to share the rights 115 with the user referenced in themessage 113. If the creator declines to share the rights 115, then therights 115 may not be shared with the user.

At block 206, the processing device may, in response to the secondrequest, send a notification to the user referenced in the message 113(example illustrated in FIG. 4). The notification may be sent to theuser device 120B of the user and presented on the user interface 124B.The notification may include an option to accept or decline the one ormore rights 115 requested to be shared by the creator of the message113.

If the user selects to accept one or more of the rights 115, at block208, the processing device may receive an acceptance of the one or morerights 115. If accepted, the rights 115 may be granted to the userreferenced in the message 113. If the user chooses to decline one ormore of the rights 115, the processing device may receive a declinationof the one or more rights 115. If declined, the rights 115 may not begranted to the user referenced in the message 113.

In some implementations, the acceptance of the one or more rights mayalso include setting one or more rules 117 specifying by the user. Therules 117 may specify one or more of sending notifications related toany responses to the message 113 to a subset of the users to which themessage 113 is sent, controlling visibility of the message 113,controlling visibility of feedback to the message 113, controllingwhether feedback is allowed for the message 113, controlling what typeof feedback is allowed for the message 113, and/or controlling who canprovide feedback for the message 113.

At block 210, the processing device may perform one or more operationsrelated to the message 113 based on the one or more rights 115 acceptedby the user (examples illustrated in FIG. 6-9). Also, the operations maybe performed based on the user rules 117 created by the user applyingthe rights 115. In an implementation, the one or more operations mayinclude sending a feedback notification, based on feedback related tothe message 113, to the user device 120B of the user referenced in themessage 113 based on the one or more rights 115 accepted by the userand/or rules 117 set up by the user. In another implementation, the oneor more operations may be performed in response to feedback (e.g.,comment, reaction, etc.) provided by other users on the message 113, andthe operations may enhance privacy and/or reduce traffic over thenetwork 130. For example, the one or more operations may enhance privacyof the user referenced in the message 113 by preventing other users fromseeing the message 113 based on a rule 117 set by the user applying theone or more rights 115, and/or by preventing other users from seeingfeedback to the message 113 based on another rule 117 set by the userapplying the one or more rights 115. In another example, the one or moreoperations may reduce message traffic over the network 130 by sending afeedback notification exclusively to the user referenced in the message113 in response to a second user providing feedback to the message 113via the user interface 1240 of the user device 120C.

FIG. 3 illustrates an example post 300 referencing a user 302 (User B)where the post 300 provides options 304 for sharing rights 115 with thereferenced user 302, in accordance with one implementation of thedisclosure. In the depiction, the post 300 is an example of the message113. In another example, an email may be used as an example of themessage 113. Although just one user 302 is referenced in the post 300,it should be appreciated that any suitable number of users may bereferenced and similar techniques may be applied. In the illustration, acreator 306 (User A) has selected an option from a messaging platform118A-118Z (e.g., social network platform) to create the post 300, and apost editing window 308 presents the post 300 in the user interface 124Aof the user device 120A of the creator 306.

The creator 306 has entered the content (e.g., “Congratulations +User Bon the successful product launch!”) of the post 300 and referenced theuser 302 within the content of the post 300 using a symbol (e.g., plussign) within the editing window 308. The user interface 124A presentingthe post 300 may include an option 310 in the post editing window 308 toset a property indicating a type of message. The type of message caninclude celebratory, congratulatory, or the like. It should beappreciated that any suitable type of message may be used that isdesirable to allow sharing rights with the user referenced in themessage. In response to selecting (represented by the darkened radiobutton) the particular type of message, the editing window 308 maypresent options 304 for sharing rights 115 of the creator 306 with theuser 302 referenced in the message.

As depicted, the options 304 may include sharing rights 115 related toreceiving feedback notifications to feedback (e.g., comments, reactions,etc.) related to the post 300, controlling whether the post 300 and/orthe feedback to the post 300 are visible to other users, and/orcontrolling whether feedback to the post 300 is allowed. The creator 306can select one or more of the options 304. In the depicted example, thecreator 306 selects (represented by the darkened radio buttons) everyoption 304. In some implementations, selecting the options may cause arequest to be sent to the server 112A-112Z running the messagingplatform 118A-118Z from the creator 306 of the post 300 to share theselected rights 115 with the user 302 referenced in the message. Theserver 112A-1122 may send one or more notifications to the referenceduser 302 where the notifications include options to accept or declinethe rights 115.

For example, FIG. 4 illustrates an example notification 400 requesting auser 302 referenced in a post 300 to accept or decline shared rights115, in accordance with one implementation of the disclosure. Thenotification 400 may be received from the server 112A-112Z and presentedto the user 302 in the user interface 124B of the user device 120B ofthe user 302 logged into the messaging platform 118A-118Z (e.g., socialnetwork platform). As depicted, the notification 400 notifies the user302 that one or more rights have been shared with the user 302 (“User Byou have been mentioned in a post and right(s) have been shared withyou, please accept or decline), and provides options 402 to accept ordecline each of the rights 115. The user 302 may select the appropriatebutton to accept or decline the shared rights 115. The acceptance ordeclination of the rights 115 may be sent from the user device 120B tothe server 112A-112Z. If the user accepts the rights 115, the rights 115may be granted to the referenced user 302. If the user declines therights 115, the rights may not be granted to the referenced user 302.

FIG. 5 illustrates example options 500 available for a referenced user302 to define the user rules 117 for posts 300 in which the user 302 isreferenced, in accordance with one implementation of the disclosure. Theoptions 500 may be presented in the user interface 124B of the userdevice 120B of the user 302 logged into the messaging platform 118A-118Z(e.g., social network platform). Although the depicted example, showsoptions 500 for creating user rules 117 applicable to any post the user302 is mentioned in, it should be appreciated that the user rules 117may be tailored to be applied to any or just a particular post 300 wherethe user 302 is granted the rights 115 and the user 302 is referenced,to posts 300 where the referenced user 302 is granted the rights 115 andthe posts 300 are made by a certain creator 306, to posts 300 where thereferenced user 302 is granted the rights 115 and the posts 300 are sentto a particular user, or group of users, and the like.

In the depicted example, a user rule 502 may specify whether the user302 enables or disables receiving notifications related to feedback tothe post 300. If the user 302 enables receiving notifications, then anytime another user comments on and/or reacts to (e.g., “likes”) the post300 in which the user 302 is referenced, the user 302 may receive anotification (examples illustrated in FIGS. 6-9).

Another user rule 504 may allow the user to specify who receivesnotifications related to feedback to the post 300. For example, a rule504 may be created in response to the user 302 specifying that thenotifications related to feedback to the post 300 are to be sentexclusively to the user 302 referenced in the post 300 (e.g., excludingany other users associated with the post 300). Such a rule may reducemessage traffic over the network by not sending notifications to thecreator 306 or other users associated with the post 300. The user rule504 may also specify sending the feedback notifications to a specificgroup of users (e.g., the creator 306 and the user 302, other users,etc.).

Another user rule 506 may specify which users the user 302 desires toview the post 300. For example, the user 302 can specify that any user(e.g., public) can view the post 300, just the user 302 (e.g., private)can view the post 300, or a subset of users (e.g., a specific group) canview the post 300. This user rule 506 may result in reducing the numberof messages sent over the network 130 when the user rule 506 restrictswhich users can view the post 300 because just those specified users mayreceive and view the post 300. Also, this user rule 506 may also resultin enhancing the privacy of certain data included in the post 300 byrestricting who can view the post 300.

Another user rule 508 may specify which users the user 302 desires toview the feedback (e.g., comments, reactions, etc.) to the post 300. Forexample, the user 302 can specify that any user (e.g., public) can viewthe feedback to the post 300, just the user 302 (e.g., private) can viewthe feedback to the post 300, or a subset of users (e.g., a specificgroup) can view the feedback to the post 300. This user rule 508 mayalso result in reducing the number of messages sent over the network 130when the user restricts which users can view the feedback to the post300 because just those specified users may receive and view feedback tothe post 300. Also, this user rule 508 may also result in enhancing theprivacy of certain data included in the feedback to the post 300 byrestricting who can view the feedback to the post 300.

Another user rule 510 may specify whether the user 302 allows feedbackto the post 300 in which the user 302 is mentioned. For example, theuser rule 510 can enable or disable allowing feedback to the post 300.If the user rule 510 enables posting feedback, another rule 512 can becreated (e.g., based on addition user input) to specify which users canprovide feedback to the post. For example, the user rule 512 can specifythat any one of the users with whom the post 300 was shared can providefeedback to the post 300. Alternatively, the user rule 512 can specifythat just a specific group of users can provide feedback to the post300. Further, if the user rule 510 enables posting feedback, anotherrule 514 can be created (e.g., based on additional user feedback) tospecify what kind of feedback is allowed. For example, the user rule 514can specify that comments on the post 300 are allowed, reactions to thepost are allowed, etc. In instances where the message 113 is an email,this user rule 514 may specify that responses to the email are allowed.

In another implementation, another rule can be created (e.g., based onuser input) specifying that that certain non-user applications (e.g.,“bots”) from certain trusted sources can view and/or provide feedback tothe post 300, while other non-user applications from untrusted sourcescannot view and/or provide feedback to the post 300. Additionally oralternatively, another rule can be created (e.g., based on our input) tospecify that certain non-user applications can view and/or providefeedback to posts 300 related to various topics. In such an instance,the server 112A-112Z may analyze the content of the post 300 todetermine whether the topic of the post 300 can be viewed and/orinteracted with. Also, in some instances, the creator 306 of the post300 may specify the topic of the post 300 when creating the post 300,and the server 112A-112Z may use the specified topic to determinewhether to allow viewing and/or providing feedback to the post 300 bythe non-user applications.

FIG. 6 illustrates an example post 600 that references a user 602 (UserB) and provides an option 604 to positively react to the post 600 toanother user 606 (User C), in accordance with one implementation of thedisclosure. The post 600 may be entered by a creator 608 (User A) andshared with a group of users (e.g., the public). The post 600 includescontent that says “Congratulations +User B on the successful productlaunch!” and references the user 602 “User B” by using a visualindicator (e.g., plus sign) to associate the post 600 with the user 602.The creator 608 may specify the property for the post 600 indicatingthat the post 600 is a particular type of message (e.g.,congratulatory). Further, the creator 608 may specify that the rights115 be shared with the user 602 referenced. For example, the creator 608may select to share the right to receive notifications related tofeedback provided by other users. In an implementation, the user 602referenced may be prompted to accept or decline the shared rights 115.In the illustrated example, the user 602 may accept the shared right 115to receive the response notifications.

The other user 606 may select the option 604 to positively react to thepost 600 congratulating the referenced user 602 in the user interface124C of the user device 124C of the user 606. The server 112A-112Z mayreceive the reaction from the user device 120C and send a notificationto the user device 120B of the user 602 referenced.

For example, FIG. 7 illustrates an example notification 700 sent to theuser 602 (User B) referenced in the post 600 when the other user 606(User C) positively reacts to the post referencing the user 602, inaccordance with one implementation of the disclosure. The notification700 may be presented in the user interface 124B of the user device 120Bof the referenced user 602. As depicted, the notification 700 includescontent that says “User B, User C has positively reacted to User A'spost congratulating you!” In this way, the user 602 referenced in thepost 600 can receive notifications when other users react to the post600.

FIG. 8 illustrates an example post 800 that references a user 602 (UserB) and provides an option 804 to comment on the post 800 to another user606 (User C), in accordance with one implementation of the disclosure.The other user 606 (User C) may be viewing the post 800 on the userinterface 124C of the user device 120C. The post 800 may be createdbased on input by a creator 608 (User A) and shared with a group ofusers (e.g., the public). The post 800 includes content that says“Congratulations +User B on the successful product launch!” andreferences the user 602 “User B” by using a symbol (e.g., plus sign) toassociate the post 800 with the user 802. The creator 608 may set theproperty for the post 800 indicating that the post 800 is a particulartype of message (e.g., congratulatory). Further, the creator 608 mayrequest to share the rights 115 with the user 602 referenced. Forexample, the creator 608 may request to share the right to receivenotifications related to feedback provided by other users. In animplementation, the user 602 referenced may be prompted to accept ordecline the shared rights 115. In the illustrated example, the user 602may accept the shared right 115 to receive the response notifications.

The other user 606 (User C) may select the option 804 to comment on thepost 600 and may post a comment that says “Way to go!” in the userinterface 124C of the user device 120C of the user 606. The server112A-112Z may receive the comment from the user device 120C and send anotification to the user device 120B of the user 602 referenced.

For example, FIG. 7 illustrates an example notification 700 sent to theuser 602 (User B) referenced in the post 600 when the other user 606(User C) positively reacts to the post referencing the user 602, inaccordance with one implementation of the disclosure.

FIG. 9 illustrates an example notification 900 sent to the user 602(User B) referenced in the post 800 when the other user 606 (User C)responds to the post referencing the user 602, in accordance with oneimplementation of the disclosure. The notification 900 may be presentedin the user interface 124B of the user device 120B of the referenceduser 602. As depicted, the notification 700 includes content that says“User B, User C has commented on User A's post congratulating you! UserC said, ‘Way to go!’ In this way, the user 602 referenced in the post800 can receive notifications when other users comment on the post 800.

FIG. 10 depicts a flow diagram of aspects of a method 1000 for analyzingcontent of a message 113 and sending a notification to a creator of themessage 113 inquiring whether the creator desires to share rights 115with a user referenced in the message 113, in accordance with oneimplementation of the disclosure. Method 1000 may be performed in thesame or a similar manner as described above in regards to method 200. Inone implementation, one or more of the operations described withreference to method 1000 may be performed by messaging platform118A-118Z executed by one or more processing devices of the servers112A-112Z. In another implementation, one or more of the operationsdescribed with reference to method 1000 may be performed by a processingdevice of the user device 120A-120Z.

Prior to method 1000 beginning, a creator may enter a message 113,reference a user in the message 113, and request that the message 113 besent to a group of users (e.g., the referenced user, other users, thecreator, etc.). In some implementations, the creator may not specify theproperty that indicates the message 113 has the type that allows sharingrights with the referenced user.

At block 1002, the processing device may analyze content of a message113 to identify if the message 113 includes one or more keywordsindicative of the particular type of message that allows sharing rightswith the referenced user. In some embodiments, the keywords may includewords indicative of congratulating the user or celebrating the user. Theprocessing device may parse the content and do string comparisons of thewords in the content to the one or more keywords. If there is a matchwith one or more words in the content of the message 113 and the one ormore keywords, the processing device may determine that the message is acandidate for the particular type of message.

As a result, at block 1004, the processing device may, based on themessage 113 including at least one of the one or more keywords, send anotification to the creator of the message 113 inquiring whether thecreator desires to share one or more rights with the referenced user.The notification may enable the creator to select which rights (e.g.,receive message/feedback notifications, control message/feedbackvisibility, control aspects related to feedback, etc.) should be sharedwith the referenced user. In some instances, the creator may select tonot share any rights 115 with the referenced user. Upon selection, theuser device 102A of the creator may send a response to the server112A-112Z.

In another implementation, if the message 113 is not set to the type ofmessage that allows sharing rights 115, the processing device mayidentify the user referenced in the message 113 and perform a search viathe Internet using the identity of the referenced user. In someembodiments, the search may be performed via a company intranet, portal,work suite of productivity applications (e.g., collaborative documentplatform), content sharing platform, or the like. If the resultsindicate the user published a recent article, developed a recentproduct, accomplished something recently, or did something else worthcongratulating and/or celebrating, the processing device may determinethat this message is intended to congratulate and/or celebrate thereferenced user. As a result, the processing device may send thenotification to the creator of the message 113 inquiring whether thecreator desires to share one or more of the rights with the referenceduser.

At block 1006, the processing device may receive a request from thecreator to share the one or more rights 115 with the referenced user. Inresponse to the request, the processing device may send a notificationto the user referenced in the message 113 including an option for theuser to accept or decline the one or more rights 115. The rights 115that are accepted by the referenced user may be granted to thereferenced user. The referenced user can view the rights 115 to decidewhether user rules 117 should be created.

FIG. 11 depicts a flow diagram of aspects of a method 1100 to allow auser to request that a creator share rights 115 to a message 113 inwhich the user is referenced, in accordance with one implementation ofthe disclosure. Method 1100 may be performed in the same or a similarmanner as described above in regards to method 200. In oneimplementation, one or more of the operations described with referenceto method 1100 may be performed by messaging platform 118A-118Z executedby one or more processing devices of the servers 112A-112Z. In anotherimplementation, one or more of the operations described with referenceto method 1100 may be performed by a processing device of the userdevice 120A-120Z.

Prior to method 1100 beginning, a creator may enter a message 113,reference a user in the message 113, and request that the message 113 besent to a group of users (e.g., the referenced user, other users, thecreator, etc.). In some implementations, the creator may not specify theproperty that indicates the message 113 has the type that allows sharingrights with the referenced user. The message 113 may be presented on theuser interface 124B of the user device 120B of the user referenced inthe message 113, as well as any other user interface of user devices ofother users to which the message is sent 113. The user interface 124Bmay provide a selectable option for the user referenced in the messageto request the one or more rights 115 to the message 113. In someinstances, the referenced user may desire to have control over aspectsof the message 113 and/or feedback to the message 113. Thus, thereferenced user may select the selectable option to request the rights115 from the creator of the message 113, and a request may be sent tothe server 112A-112Z.

At block 1102, the processing device may receive the request for acreator of the message 113 to share the one or more rights 115 with theuser. At block 1104, the processing device may send a notification tothe creator of the message inquiring whether the creator desires toshare the one or more rights 115 with the user. The creator may selectto grant every right 115 requested, a subset of the rights 115requested, or none of the rights 115 requested. The selections of thecreator may be sent as a request to share the rights 115 from the userdevice 120A of the creator to the server 112A-112Z.

At block 1106, the processing device may receive the request from thecreator to share the one or more rights 115 with the referenced user. Inresponse to receiving the request, the processing device may send anotification to the user referenced in the message 113 including one ormore options to accept or decline the shared rights 115. The rights 115that are accepted by the referenced user may be granted to thereferenced user. The referenced user can apply the rights 115 to createuser rules 117.

FIG. 12 depicts a block diagram of an example computing system operatingin accordance with one or more aspects of the present disclosure. Invarious illustrative examples, computer system 1200 may correspond toany of the computing devices within system architecture 100 of FIG. 1.In one implementation, the computer system 1200 may be each of theservers 112A-112Z. In another implementation, the computer system 1200may be each of the user devices 120A-120Z.

In certain implementations, computer system 1200 may be connected (e.g.,via a network, such as a Local Area Network (LAN), an intranet, anextranet, or the Internet) to other computer systems. Computer system1200 may operate in the capacity of a server or a client computer in aclient-server environment, or as a peer computer in a peer-to-peer ordistributed network environment. Computer system 1200 may be provided bya personal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, switch or bridge, or any device capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that device. Further, the term “computer” shallinclude any collection of computers that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methods described herein.

In a further aspect, the computer system 1200 may include a processingdevice 1202, a volatile memory 1204 (e.g., random access memory (RAM)),a non-volatile memory 1206 (e.g., read-only memory (ROM) orelectrically-erasable programmable ROM (EEPROM)), and a data storagedevice 1216, which may communicate with each other via a bus 1208.

Processing device 1202 may be provided by one or more processors such asa general purpose processor (such as, for example, a complex instructionset computing (CISC) microprocessor, a reduced instruction set computing(RISC) microprocessor, a very long instruction word (VLIW)microprocessor, a microprocessor implementing other types of instructionsets, or a microprocessor implementing a combination of types ofinstruction sets) or a specialized processor (such as, for example, anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), or a networkprocessor).

Computer system 1200 may further include a network interface device1222. Computer system 1200 also may include a video display unit 1210(e.g., an LCD), an alphanumeric input device 1212 (e.g., a keyboard), acursor control device 1214 (e.g., a mouse), and a signal generationdevice 1220.

Data storage device 1216 may include a non-transitory computer-readablestorage medium 1224 on which may store instructions 1226 encoding anyone or more of the methods or functions described herein, includinginstructions implementing the messaging platform 118 (118A-118Z) and/orthe user interface 124 (124A-124Z) of FIG. 1 for implementing themethods described herein.

Instructions 1226 may also reside, completely or partially, withinvolatile memory 1204 and/or within processing device 1202 duringexecution thereof by computer system 1200, hence, volatile memory 1204and processing device 1202 may also constitute machine-readable storagemedia.

While computer-readable storage medium 1224 is shown in the illustrativeexamples as a single medium, the term “computer-readable storage medium”shall include a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of executable instructions. The term“computer-readable storage medium” shall also include any tangiblemedium that is capable of storing or encoding a set of instructions forexecution by a computer that cause the computer to perform any one ormore of the methods described herein. The term “computer-readablestorage medium” shall include, but not be limited to, solid-statememories, optical media, and magnetic media.

In the foregoing description, numerous details are set forth. It will beapparent, however, to one of ordinary skill in the art having thebenefit of this disclosure, that the present disclosure can be practicedwithout these specific details. In some instances, well-known structuresand devices are shown in block diagram form, rather than in detail, inorder to avoid obscuring the present disclosure.

Some portions of the detailed description have been presented in termsof algorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, for reasons of common usage, to refer tothese signals as bits, values, elements, symbols, characters, terms,numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “receiving”, “displaying”, “moving”, “adjusting”,“replacing”, “determining”, “playing”, or the like, refer to the actionsand processes of a computer system, or similar electronic computingdevice, that manipulates and transforms data represented as physical(e.g., electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

For simplicity of explanation, the methods are depicted and describedherein as a series of acts. However, acts in accordance with thisdisclosure can occur in various orders and/or concurrently, and withother acts not presented and described herein. Furthermore, not allillustrated acts can be required to implement the methods in accordancewith the disclosed subject matter. In addition, those skilled in the artwill understand and appreciate that the methods could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be appreciated that the methodsdisclosed in this specification are capable of being stored on anarticle of manufacture to facilitate transporting and transferring suchmethods to computing devices. The term article of manufacture, as usedherein, is intended to encompass a computer program accessible from anycomputer-readable device or storage media.

Certain implementations of the present disclosure also relate to anapparatus for performing the operations herein. This apparatus can beconstructed for the intended purposes, or it can comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program can be stored ina computer readable storage medium, such as, but not limited to, anytype of disk including floppy disks, optical disks, CD-ROMs, andmagnetic-optical disks, read-only memories (ROMs), random accessmemories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any typeof media suitable for storing electronic instructions.

Reference throughout this specification to “one implementation” or “animplementation” means that a particular feature, structure, orcharacteristic described in connection with the implementation isincluded in at least one implementation. Thus, the appearances of thephrase “in one implementation” or “in an implementation” in variousplaces throughout this specification are not necessarily all referringto the same implementation. In addition, the term “or” is intended tomean an inclusive “or” rather than an exclusive “or.” Moreover, thewords “example” or “exemplary” are used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the words“example” or “exemplary” is intended to present concepts in a concretefashion.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other implementations will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the disclosure should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

Further to the descriptions above, a user may be provided with controlsallowing the user to make an election as to both if and when systems,programs or features described herein may enable collection of userinformation (e.g., information about a user's social network, socialactions or activities, profession, a user's preferences, or a user'scurrent location), and if the user is sent content or communicationsfrom a server. In addition, certain data may be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over what information is collected about the user,how that information is used, and what information is provided to theuser.

1. A method comprising: receiving, at a server, a request from a creatorof a message to share one or more rights of the creator of the messagewith a user referenced in the message, wherein the message is for aplurality of users and the user; in response to the request, sending, bythe server, a notification to the user referenced in the message,wherein the notification includes an option to accept the one or morerights; receiving, at the server from a user device of the user, anacceptance of the one or more rights; and performing, by the server, oneor more operations related to the message based on the one or morerights accepted by the user.
 2. The method of claim 1, wherein themessage is at least one of a social media post in a social networkplatform, an email in an email system, or a text or multimedia messagein a text messaging platform or a video conferencing platform.
 3. Themethod of claim 1, wherein the one or more operations comprise sending afeedback notification, based on feedback related to the message, to theuser based on the one or more rights accepted by the user.
 4. The methodof claim 1, wherein performing one or more operations comprisespreventing other users of the plurality of users from seeing the messagebased on a first rule set by the user with respect to the one or morerights, or preventing other users of the plurality of users from seeingfeedback to the message based on a second rule set by the user withrespect to the one or more rights.
 5. The method of claim 1, whereinperforming the one or more operations comprises sending a feedbacknotification exclusively to the user referenced in the message inresponse to a second user of the plurality of users providing feedbackto the message.
 6. The method of claim 1, wherein performing the one ormore operations comprises sending a feedback notification exclusively tothe creator and the user referenced in the message in response to asecond user of the plurality of users providing feedback to the message.7. The method of claim 1, wherein receiving, from the user device of theuser, the acceptance of the one or more rights further comprises settingone or more rules specifying one or more of sending notificationsrelated to any responses to the message to a subset of the plurality ofusers, controlling visibility of the message, controlling visibility offeedback to the message, controlling whether feedback is allowed for themessage, controlling what type of feedback is allowed for the message,or controlling who can provide feedback for the message.
 8. The methodof claim 1, wherein the request includes a property indicating themessage being of a type of message that specifies to share the one ormore rights of the creator of the message with the user identified inthe message.
 9. The method of claim 1, wherein the method furthercomprises: analyzing content of the message to identify if the messagecomprises one or more keywords indicative of a particular type ofmessage; and based on the message comprising at least one of the one ormore keywords, sending a second notification to the creator of themessage, wherein the second notification inquires whether the creatordesires to share the one or more rights with the user and the secondrequest is received as a response to the second notification.
 10. Themethod of claim 1, wherein the method further comprises: receiving, atthe server from the user device of the user, a request for the creatorto share the one or more rights with the user; and sending a secondnotification to the creator of the message, wherein the secondnotification inquires whether the creator desires to share the one ormore rights with the user and the second request is received as aresponse to the second notification.
 11. The method of claim 1, whereinthe one or more rights specify one or more of whether the user is toreceive feedback notifications of feedback related to the message,whether the user is to control visibility of feedback on the message byusers, or whether the user is to control allowing feedback on themessages.
 12. The method of claim 1, wherein the one or more operationsare performed in response to a second user of the plurality of usersproviding feedback on the message, wherein the feedback comprises areaction or a comment.
 13. A system comprising: a memory device; and aprocessing device operatively coupled to the memory device, theprocessing device to: receive a request from a creator of a message toshare one or more rights of the creator of the message with a userreferenced in the message, wherein the message is for a plurality ofusers and the user; in response to the request, send a notification tothe user referenced in the message, wherein the notification includes anoption to accept the one or more rights; receive, from a user device ofthe user, an acceptance of the one or more rights; and perform one ormore operations related to the message based on the one or more rightsaccepted by the user.
 14. The system of claim 13, wherein the message isat least one of a social media post in a social network platform, anemail in an email system, or a text or multimedia message in a textmessaging platform or a video conferencing platform.
 15. The system ofclaim 13, wherein performing one or more operations includes theprocessing device further to prevent other users of the plurality ofusers from seeing the message based on a first rule set by the user withrespect to the one or more rights, or preventing other users of theplurality of users from seeing feedback to the message based on a secondrule set by the user with respect to the one or more rights.
 16. Thesystem of claim 13, wherein receiving, from the user device of the user,the acceptance of the one or more rights further comprises setting oneor more rules specifying one or more of sending notifications related toany responses to the message to a subset of the plurality of users,controlling visibility of the message, controlling visibility offeedback to the message, controlling whether feedback is allowed for themessage, controlling what type of feedback is allowed for the message,or controlling who can provide feedback for the message.
 17. The systemof claim 13, wherein the request includes a property indicating themessage being of a type of message that specifies to share the one ormore rights of the creator of the message with the user identified inthe message.
 18. A non-transitory, computer readable media storinginstructions that, when executed, cause a processing device to: receivea request from a creator of a message to share one or more rights of thecreator of the message with a user referenced in the message, whereinthe message is for a plurality of users and the user; in response to therequest, send a notification to the user referenced in the message,wherein the notification includes an option to accept the one or morerights; receive, from a user device of the user, an acceptance of theone or more rights; and perform one or more operations related to themessage based on the one or more rights accepted by the user.
 19. Thecomputer readable media of claim 18, wherein the processing device isfurther to: analyze content of a response to the message to identify ifthe response comprises one or more keywords indicative of a particulartype of message; and based on the response comprising at least one ofthe one or more keywords, send a second notification to the creator ofthe message, wherein the second notification inquires whether thecreator desires to share the one or more rights with the user and thesecond request is received as a response to the second notification. 20.The computer readable media of claim 18, wherein the processing deviceis further to: receive, from the user device of the user, a request forthe creator to share the one or more rights with the user; and send asecond notification to the creator of the message, wherein the secondnotification inquires whether the creator desires to share the one ormore rights with the user and the second request is received as aresponse to the second notification.